Testing Operator
A maximum of three Teams test tenants should be allocated for preproduction testing. If the operator does not have a production environment available, they can leverage SIP trunks over the internet using TLS. The Operator must integrate at least the following APIs with the Operator’s BSS System:
| ■ | Partner Consent |
| ■ | TN Upload To Account |
| ■ | Call Duration |
|
Task |
Action |
System |
|---|---|---|
|
Test Consent |
Grant consent from one of the Teams test tenants whitelisted for private preview |
Teams admin center |
|
Retrieve consent from Operator Connect portal |
Operator Connect portal |
|
|
Retrieve consent from API call |
Postman or some other HTTP tool |
|
|
Determine how best to integrate into BSS |
Operator’s BSS |
|
| Test TN Upload |
Upload TN to Teams test tenants whitelisted for private preview |
Preference is to use API to do this upload |
|
Assign TNs ( Assign at least 2 to 3 TNs to test users in teams test tenant) |
Teams admin center |
|
|
Make outbound calls |
Microsoft Teams client |
|
|
View Teams CDR |
Teams admin center |
|
| Call Duration |
Post Call Duration |
Preference is to use API to do this upload |
|
View Teams CDR to confirm call duration is listed from Operator |
TAC |
|
|
Unassign TN and release TN* |
Unassign TN and release TN |
TAC |
|
Pull Acquired Numbers |
Preference is to use API to retrieve file |
|
|
Test SIP Calling Functionality |
Configure SLA testing numbers for your Offer type (Calling, AudioConferencing and Mobile) in the Calling Profile Management page and then run the automation tests. |
Operator Connect portal |